Re-deploying loops in a Process+ Action Object

Redeployment is the term used when some or all of the control loops of an Action Object, that has completed executing, are removed from that Action Object and reused in a different Action Object.

Redeploying loops within another Action Object saves time - loop data is maintained, and the loop information has already been prepared to the correct format for deployment.

NOTE: In a distributed deployment with multiple CSense Runtime servers connecting to a shared data server, control loops belonging to an Action Object are only visible on the CSense Runtime server it was deployed on. If the Action Object is removed but the control loops are kept, the control loops become visible to all CSense Runtime servers for redeployment.

Step 1: Identify loops that can be redeployed

All loop information that is currently stored within the Process+ CSense Runtime Manager can be viewed by clicking [Loops].
Loop information such as the loop ID, loop description, and the Action Object to which it is currently assigned is listed.
If the loop is not assigned to an Action Object, there will be no Action Object name listed next to the loop.
Only loops not already part of an Action Object can be redeployed.

Step 2: Making loops available for redeployment

The Action Object that initially deployed the control loops needs to have been removed.

When removing the Action Object, if you selected to leave the box unchecked in the pop up dialog, the loop configuration information and calculated Proces+ KPIs from these loop will be kept; only the Action Object will be removed from the CSense Runtime Manager. Keeping the loops enables you to redeploy these loops as part of another Action Object at a later date.

Step 3: Redeploying loops

Creating the loop definitions .csv file:

When adding an Action Object to the CSense Runtime Manager for deployment, a loop definitions file is selected among the other configuration steps. This .csv file lists details of the control loops, including the sampling period and the number of loops to be deployed in the Action Object.
This .csv file detailing the control loop information needs to be created before any Action Object can be deployed, or redeployed.
As part of the file, you need to know the LoopID.
Read the LoopID off the loop definitions .csv file from the initial deployment of the loop.
Manually enter the LoopID into the new .csv file LoopID column. See an example here.

Add a Process+ Action Object:

Once the new loop definitions file has been created, continue to add a new Action Object redeploying loops previously used, and/or deploying new control loops.